Methods and systems for wallet enrollment

ABSTRACT

Embodiments of the present invention relate to systems, methods, processes, computer program code, and means for creating digital wallets for users. In some embodiments, digital wallets are created, at least in part, on information obtained from payment transactions conducted by users.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/136,843 filed on Apr. 22, 2016, which in turn isa continuation of and claims the benefit of U.S. patent application Ser.No. 13/902,458 filed on May 24, 2013, which in turn claims the benefitof U.S. Provisional Patent Application No. 61/651,193 filed on May 24,2012, the entirety of each of which is incorporated herein by reference.

BACKGROUND

Consumers continue to seek faster, more convenient and more secure waysto pay for goods and services, pay bills, pay other people (peer-to-peeror person to person) and access cash at ATMs. In some cases this meansconducting these transactions without the use of plastic payment cards.For example, the inventor of the instant application described systemsand methods for using mobile devices (such as mobile phones) to conductpurchase transactions in U.S. Pat. No. 8,380,177, the contents of whichare hereby incorporated herein in their entirety for all purposes.

Many card-less, online or mobile transaction systems require that usersregister one or more payment devices or accounts with a so-called“digital wallet”. The digital wallet stores information about the userand the payment device(s), allowing the payment device(s) to be used intransactions involving the digital wallet. Unfortunately, adoption ofsuch digital wallets requires that users enroll or otherwise provideinformation to the entity operating the digital wallet (includingpayment card details, user details, and the like). For example, somedigital wallets require the user to navigate a Web browser to a walletenrollment website, enter a portion of the data associated with aplastic payment card (or other payment account) into an enrollment form,and provide other authenticating information. This process can be timeconsuming, error prone, subject to fraud, and inconvenient for potentialusers.

As digital wallets become more prevalent, users will want to store manyor all of their account information in the new wallet which makes theprocess even more time consuming. This difficult registration processmakes it much less likely users will adopt alternate payment methods andcreates a barrier to broader, merchant and financial institutionacceptance.

It would be desirable to provide a convenient and secure way for usersto register payment credentials with a digital or mobile wallet serviceand thus enable more rapid adoption of alternative payment methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system configured pursuant to someembodiments.

FIG. 2 is a flow diagram depicting a process pursuant to someembodiments.

FIG. 3 is a block diagram depicting a point of transaction devicepursuant to some embodiments.

FIG. 4 is a flow diagram depicting a process pursuant to someembodiments.

FIG. 5 is an illustrative user interface of a point of transactiondisplay pursuant to some embodiments.

DESCRIPTION

Embodiments of the present invention relate to systems, methods,processes, computer program code, and means for creating digital walletsfor users. In some embodiments, digital wallets are created, at least inpart, on information obtained from payment transactions conducted byusers. For example, in some embodiments, a seed data record in a digitalwallet system may be created for a user based on information obtainedduring a payment transaction conducted by that user. For example, theinformation may be obtained during a purchase transaction at a merchantin which the user presents a traditional credit card (or other paymentdevice) to a merchant at a point of sale (in person at a physical pointof sale or remotely in a mail order, telephone or Internet transaction).In some embodiments, payment details and user information obtainedduring the purchase transaction may be transmitted to a walletenrollment system for use in creating a seed data record in a digitalwallet system. Additional details may be provided by the user at a latertime (e.g., in response to a notification message transmitted by thedigital wallet system to the user). In this way, embodiments allow thecreation of digital wallets on behalf of users efficiently and securely.Further, embodiments provide merchants and other entities with theability to market and encourage use of digital wallets by prompting themto enroll while at a point of sale. In this way, merchants candramatically accelerate consumer adoption of digital wallets.

As used herein, the term “payment device”, “payment card” or “creditcard” is used to refer to a device, card or indicator used to initiatepayment or purchase transactions. For example, a payment device may be atraditional credit card, debit card, or similar device that may bepresented to a merchant or other entity by an account holder to completea financial transaction.

As used herein, the term “digital wallet” is used to refer to anelectronic repository of payment or other account information such as,for example, a mobile payment application that accesses accountinformation stored at one or more central repositories. For example, oneform of digital wallet that may be used with desirable results inconjunction with embodiments of the present invention is the digitalwallet (or mobile payment application) shown and described in ourco-pending and commonly assigned U.S. patent application Ser. No.13/768,156 and U.S. Pat. No. 8,380,177, the contents of each of whichare hereby incorporated by reference in their entirety for all purposes.Those skilled in the art, upon reading the following disclosure, willappreciate that embodiments of the present invention may be used withdesirable results in conjunction with other “digital wallet”technologies such as, for example, electronic wallets accessible online(such as, for example, the Google® Wallet, PayPal®, V.ME from Visa® orthe like). For example, a wallet accessible online (e.g., via a Webbrowser) may be referred to as a “browser wallet”, while a walletaccessible through a mobile application may be referred to as a “mobilewallet”. Some wallets may be accessible through both a mobileapplication as well as a browser. For convenience and ease ofexposition, each of these wallets may be referred to herein as a“digital wallet”.

Embodiments of the present invention relate to systems, methods,processes, computer program code and means for enrolling in and creatinga digital/mobile wallet account that can be used on a mobile device orany other network (such as Internet) connected device to conductfinancial transactions in a variety of contexts including retail stores,restaurants, ecommerce sites, bill payment, ATM cash access and betweenindividuals. In some embodiments, the account and wallet creationprocess is initiated at a brick and mortar point-of-sale terminal, whena retailer processes a payment card as part of a traditional card-basedpayment transaction. In some embodiments, the card can include but isnot limited to credit, debit, stored, value and even checking, savingsand other bank accounts. In some embodiments, the card can be a loyalty,reward, or other benefits card.

For the purposes of describing features of some embodiments, anillustrative example will be described (and referenced throughout theremainder of this disclosure). This illustrative example is not intendedto be limiting—instead, it is used to provide an example of someembodiments. In the illustrative example, an individual (the “customer”)has several payment cards, including a debit card issued by a first bank(referred to as “First Bank”) and a credit card issued by a second bank(referred to as “Second Bank”). Both of the payment cards aretraditional form factor magnetic stripe cards (e.g., they are compliantwith ISO Standards 7810, 7812 and 7813, for example). In theillustrative example, the customer is conducting a transaction at aretail store. In particular, the customer has presented a number ofitems to a store clerk, who has rung up the items on a store point ofsale device. The customer chooses to pay using his debit card, andpresents the card for payment (e.g., by swiping the magnetic stripe cardthrough a customer-facing point of sale device, or by providing the cardto the clerk, etc.).

Pursuant to embodiments of the present invention, several things occurat this point in the transaction. First, data from the payment card(e.g., such as magnetic stripe data read from Track 1 and/or Track 2 ofthe card) are used to establish a traditional payment authorizationrequest (for submission to a payment network for processing of thetransaction). Further, pursuant to some embodiments, the same (orsimilar) data from the payment card is used to establish a walletregistration request message. This wallet registration request messagecan be initiated by the point of sale terminal or it can be initiatedelsewhere in the authorization processing network (e.g., such as at anacquirer, an issuer, a merchant processor, a gateway, or in the paymentnetwork itself). In some embodiments, generation (and transmission) ofthe wallet registration request message may require permission oracceptance by the customer. In some embodiments, this permission oracceptance is obtained at the point of sale (e.g., by presenting amessage to the customer on a customer facing point of sale device, suchas that shown and described below in conjunction with FIG. 5 ). In someembodiments, the customer permission or acceptance includes the receiptof a contact method for the customer, such as, for example, a mobiletelephone number, an email address or the like.

Once acceptance or permission is obtained, the wallet registrationrequest message is transmitted to a wallet enrollment system for furtherprocessing. In situations where the customer does not currently have adigital wallet, the wallet enrollment system provisions or creates adigital wallet on behalf of the customer. The provisioning of thedigital wallet includes associating the received payment card data(e.g., from Track 1 and/or Track 2 of the payment card or the like) withthe customer's digital wallet. In some embodiments the actual paymentaccount information (such as the primary account number or “PAN” andother sensitive information) is stored in a secure manner and associatedwith the digital wallet using a proxy identifier or the like. Once thedigital wallet is provisioned, information is transmitted from thewallet enrollment system (or from a system under control of the walletenrollment system) to the customer (using the contact method provided bythe customer) with instructions for accessing the newly provisioneddigital wallet. In this manner, embodiments allow customers to easilyregister or associate payment card information with a wallet (as well asto create a new digital wallet). For example, in some embodiments, uponelectronically or otherwise collecting (including by manual keypadentry) payment account information from a payment card, the account datais not only transmitted via traditional channels to a payment processor,but given customer approval, is also transmitted to a wallet enrollmentsystem to initiate the account creation process.

In the illustrative example, the customer may later wish to add hiscredit card (from Second Bank) to his previously created digital wallet.Pursuant to some embodiments, additional payment cards can easily beadded when the customer uses the additional payment card at a point ofsale, and when prompted whether the card should be added to a digitalwallet, the customer may consent and enter contact information that ispreviously associated with the existing digital wallet. The contactinformation may then be used to identify the existing digital wallet andinformation associated with the new payment card may be associated withthe existing digital wallet of the customer.

In some embodiments, when a payment card is added (e.g., in response toa wallet registration request message) to a new (or existing) digitalwallet, the payment card record in the wallet is considered to be a“seed” or partial record, and additional steps may be required from thecustomer to complete the information about the payment card in thewallet (e.g., to verify the customer's ownership of the account, toprovide usage rules, to provide name, address and other contactinformation, or the like). In some embodiments, the contact methodprovided by the customer may be used to communicate information to thecustomer to obtain the additional information required to complete therecord. As used herein, the term “seed record” will be used to refer topayment account data associated with a digital wallet which requiresadditional information from a holder of the payment account. While theterm “record” is used, it is not intended to imply that a single recordor field of a database or data table contains the information—instead,the term “record” is used merely for convenience and ease of exposition,and is intended to refer to any data storage technique in which dataassociated with an account may be stored in association with a digitalwallet.

The initial account data including but not limited to customer name,account identification number, expiration date and other necessaryinformation, is used to “seed” the account creation process. Once theinitial account setup is completed, the wallet enrollment system sendsan email, text message or otherwise notifies the user that an accounthas been created in their name. This notification includes a link,button or other means of navigating to an application or website forcompleting the enrollment process.

Once the customer installs the mobile application or navigates to a Website associated with the wallet provider, they may or may not berequired to enter additional information. At a minimum it is expectedthe customer will need to create account authentication credentials thatmay include but are not limited to a username, email address, password,PIN or other identifying information. This information will be used toauthenticate further access to the digital wallet to change accountinformation, user profile information or other user data. Those skilledin the art will appreciate there are a number of activities a user maywish to conduct as part of digital wallet account maintenance.

Once the registration process is complete, the customer now has a validdigital wallet that can be accessed by any number of alternative paymentmechanisms or applications including mobile payment, ecommerce payments,peer-to-peer (or person to person) payments, bill payments and ATM cashaccess.

Embodiments of the present invention are believed to provide desirableadvantages when compared to existing methods for user and paymentaccount enrollment in alternative payment wallets. First, it provides aconvenient process for retailers and other merchants to encourageregistration for a digital wallet at the time of payment. In this way,consumers that are using traditional methods of payments can beencouraged to enroll for an alternative payment method as part of thenormal payment process. This will create numerous opportunities to drivecustomer adoption as part of the normal daily business process.

Another advantage is customer convenience. Registering payment accountscan be a time consuming process whether it is entering credit cardinformation, address data for an e-commerce site, or adding accountinformation to an existing alternative payments platform like PayPal. Itis widely believed that these existing registration processes are aprimary deterrent to using alternative, digital or mobile paymentsystems. By reducing the enrollment and account creation process to acard swipe and a sharing of contact information (such as a mobile phonenumber or email address), the time required to register is dramaticallyreduced for the consumer.

Another advantage is the reduction of fraud in the digital walletaccount creation process. Because physical payment cards are physicallyswiped at a point of sales system, fraud due to entering a stolen cardnumber—a primary source of e-commerce fraud for example—is eliminated orsubstantially reduced. Only customers in physical possession of the carditself can initiate the enrollment process as part of a paymenttransaction. The payment transaction itself also helps reduce fraud insubsequent transactions since a successful payment transaction with nochargeback is a good indicator of valid credential data. Furthermore,the addition of the mobile number or email address adds another “factor”to the authentication process. This also reduces risk since it combinesthe physical card with an additional credential that can be furthervalidated if necessary.

Features of some embodiments of the present invention will be describedby reference to FIG. 1 , which is a block diagram of a system 100pursuant to some embodiments. As shown, the system 100 has a number ofentities or devices which interact to facilitate the efficientenrollment in and provisioning of a digital wallet for a user. Further,the entities or devices of the system 100 may allow the efficientenrollment or registration of additional payment accounts or devices inexisting digital wallets.

In the system of FIG. 1 , a user paying for goods at a retail storeapproaches the cashier and begins to conduct a transaction in thetraditional manner using a payment device 102. In some embodiments, thepayment device could be a credit, debit, stored value or other type ofpayment card. The transaction may be conducted as a card presenttransaction (e.g., by swiping or presenting the payment card to aphysical point of sale system) or it may be a card not presenttransaction (e.g., where the user enters card information into anelectronic shopping cart or provides the card information over thephone). In some embodiments, such as for physical card presenttransactions, on presenting the card 104 at a point of sale of themerchant system 106, the clerk may be prompted on a display of a pointof sale device of merchant system 106 to ask the user whether they wouldlike to enroll information associated with the payment card 102 into adigital wallet and/or to create a new digital wallet. In otherembodiments, the prompt to enroll the card may appear on a customerfacing display of a point of sale device, or in an online shopping cart.The user may agree to enroll the payment card 102 in a digital wallet(and/or to create a new digital wallet with the payment cardinformation) by either replying verbally to the clerk or selecting “yes”(or other affirmative choice) on a display and/or keypad of a point ofsale device themselves. The clerk may also ask the user for their mobilephone number and/or email address to complete the transaction. In otherembodiments, this request may appear on a customer facing display device(such as shown in FIG. 5 ) or in an electronic shopping cart, and theuser may enter this information rather than a clerk. In otherembodiments, the user may also be prompted to swipe their driver'slicense 103 or other identifying information in order to retrieve theirhome address information as well.

Once the user has accepted the offer to create or update a digitalwallet using information associated with the payment card 102, themerchant system 106 generates and transmits a payment authorizationrequest (including the data read from the payment card 102 as well astransaction details associated with the purchase transaction conductedbetween the cardholder and the merchant) to a payment processor 108using a traditional processing network connection 107. For example, themerchant system 106 may post data to a payment gateway or otherwisetransmit payment card and transaction data to a payment processor 108for payment processing in a conventional manner.

Pursuant to embodiments of the present invention, the merchant system106 also transmits (or causes the transmission of) payment cardinformation and cardholder contact information (such as a mobile phonenumber, an email address, or the like) to a wallet enrollment system 114over a network connection 110. For example, the payment card and contactinformation may be formed in a wallet request message and transmitted tothe wallet enrollment system 114 via a secure API or the like. In someembodiments, the wallet request message is generated by an entity otherthan the merchant system 106. For example, in some embodiments, themerchant system 106 may flag those transactions in which a cardholderhas opted in to allowing the payment card to be used in a walletregistration process pursuant to the present invention. The flag may beset in one or more fields such that a payment processor 108 associatedwith the merchant system 106 may identify those transactions in whichthe cardholder has opted in to permitting use of the payment card to beused in an wallet registration process, and then the payment processor108 may generate a wallet request message which is transmitted to walletenrollment system 114 for enrollment processing. In some embodiments,both a flag (or other data element) indicating customer consent as wellas data identifying a customer contact method may be provided. Forexample, the customer contact method may include information identifyinga preferred method by which the customer wishes to be contacted once thedigital wallet has been provisioned by wallet enrollment system114(e.g., such as a mobile phone number, an email address, or the like).

That is, in some embodiments, the merchant systems 106 transmits thewallet request message to the wallet enrollment system 114, and in someembodiments, the payment processor 108 transmits the wallet requestmessage to the wallet enrollment system 114. In either embodiment, thewallet request message may include information from the payment card 102used in a transaction at the merchant (e.g., such as Track 1/Track 2data read from a magnetic stripe, or the like).

The wallet enrollment system 114 combines the payment card data whichmay include (but is not limited to): a payment card number (alsoreferred to as a “PAN”), a payment card expiration date, and a customername. Customer contact information may also be provided (if captured bythe merchant systems as described herein), such as, for example, amobile phone number, an email address, or the like. In some embodiments,if a driver's license was successfully scanned by the merchant system106, the data transmitted to the wallet enrollment system 114 data mayalso include the cardholder's home address and other information. If thecustomer did not previously have a digital wallet provisioned, this data(received by the wallet enrollment system 114 from a wallet requestmessage or messages) is used to create a new “seed” digital walletaccount in the customer's name with the swiped payment card as theinitial payment instrument in the digital wallet. If the customer didpreviously have a digital wallet provisioned, this information from thewallet request message is used by the wallet enrollment system 114 toupdate an existing digital wallet of the customer (by adding the newpayment card to the existing digital wallet of the customer).

Pursuant to some embodiments, the provisioning of a new digital walletmay include the storage of the received payment card information in asecure storage device or network, and generating an identifier (or“proxy”) which allows the digital wallet to reference the payment cardinformation in the secure storage device or network. The proxy mayfurther be associated with a wallet identifier assigned to the newcustomer. In this manner, a digital wallet may be created that is seededwith basic information associated with the customer, including thecustomer contact information (such as mobile phone number) and a proxyor identifier usable to lookup or retrieve the payment card information.

Subsequent to creating the seed digital wallet account, the walletenrollment system 114 may send a notification message to the user (usingthe contact preference information provided by the user). For example,the system 114 may cause a text message 118 to be sent to the user'smobile device 122 with a link to install a mobile wallet application.The user will select this link and install the mobile application inorder to complete the registration process. In other embodiments, thewallet enrollment system may use an email message 124 to send to promptusers of a mobile phone or a personal computer 130 to complete theirregistration and/or install the mobile application.

Once the mobile application is installed, the user will be asked toenter any remaining necessary account information needed to complete theconfiguration and setup of the digital wallet. For example, the user maybe prompted to enter their home address, their billing address, theirpreferred shipping address, and other contact information (such asalternative phone numbers and email address). Other required informationmay include additional account credentials, social security number,password selection, password hints and other information. Those skilledin the art will appreciate that other pieces of information may becollected pursuant to the present invention.

Once the registration process is complete, the user is now able to usetheir digital wallet using their mobile or internet connected device topurchase goods or services, pay bills or access cash at ATMs. Thedigital wallet is presented on the mobile or other Internet connecteddevice as a series of accounts available for payment. After the goodsand/or services have been totaled, the payment method is selected andthe transaction conducted.

Although a single wallet enrollment system 114 is shown in FIG. 1 , anynumber of such devices may be included. Moreover, various devicesdescribed herein might be combined according to embodiments of thepresent invention. For example, in some embodiments, the walletenrollment system, the payment processor, and the merchant (orcombinations thereof) might be co-located and/or may comprise a singleapparatus. The wallet enrollment system 114 may be implemented as one ormore server or other computing devices which include one or morecomputer processors which may include one or more conventionalmicroprocessors and may operate to execute programmed instructions toprovide functionality as described herein. The wallet enrollment system114 may be, according to some embodiments, accessible via a GraphicalUser Interface (GUI) rendered at least in part by one or moreinput/output controllers. The GUI might be used, for example, to allowaccess to wallet information or the like by one or more users and/oradministrators.

Reference is now made to FIG. 2 , where a process 200 for creating awallet account pursuant to some embodiments is described. Process 200may be performed by a system such as the system 100 of FIG. 1 . Forexample, process 200 may be performed in association with a purchasetransaction conducted by a customer of a merchant system 106. Althoughembodiments are described as being performed in conjunction with apurchase transaction, embodiments may also be used in a registrationprocess, where a customer swipes or presents a payment device in orderto create a “seed” record in a digital wallet, without conducting apayment transaction.

Processing begins at 202 where a wallet enrollment system 114 (or otherdevice operated to perform the processing of FIG. 2 ) receivestransaction data from a payment transaction involving a user and apayment device. For example, the transaction data may be received from amerchant point of sale location at which a user has presented a paymentdevice for a purchase transaction. The transaction processing at themerchant may proceed as a normal transaction; however, some or all ofthe transaction data may be transmitted (in parallel, in real time, orin a batch mode) to the wallet enrollment system 114 at 202, including,for example, data from Track 1 and/or Track 2 of a magnetic stripe ofthe payment device, as well as information identifying the user. Forexample, processing at 202 may include transmitting or preparing totransmit the following information to the wallet enrollment system: theuser's name, the primary account number (“PAN”) of the payment device,and an expiry date. In some embodiments, the user may be prompted toprovide additional information such as an email address, a phone number,or the like.

In some embodiments, at 204, either before or after a payment device ispresented, the user is prompted (e.g., prior to or in conjunction withthe purchase transaction) to consent to transmitting some or all of theinformation to the wallet server (e.g., by being prompted by a clerk atthe merchant location, or by accepting terms and conditions on a displayscreen associated with the point of sale device, or the like). Forexample, an illustrative user interface 500 for prompting for suchinformation is shown in FIG. 5 (where a user interface 500 that may bedisplayed on a display device 502 at a point of transaction is shown).

At 206, the wallet enrollment system 114 receives the information andcreates a seed record in a wallet database on behalf of the user. Asused herein, the term “seed record” generally refers to a partial recordthat either requires additional information to be a complete record foruse (e.g., such as additional user information or additional paymentaccount information) or that requires verification or confirmation bythe user. In some embodiments, a seed record may be created for anexisting user, where the seed record may be associated with an existingdigital wallet associated with a current user, and the seed recordincludes payment account information for a new payment account to beassociated with the user. For example, a user who has alreadyestablished an existing digital wallet with payment account details fora Visa® credit card, and who is conducting a purchase transaction usinga MasterCard® debit card may have details of the MasterCard debit cardadded as a seed record associated with his existing digital walletaccount. In this manner, embodiments allow users to easily, securely andaccurately add payment account details to their digital wallet.

Processing continues at 208 where the user is notified of the creationof the seed record. For example, this notification may be transmitted tothe user as an email message, as a text message, as a phone call or thelike, prompting the user to verify details in the seed record and to addany additional data needed to convert the seed record to an activerecord. This notification may be used as a security mechanism to ensurethat the user authorized the creation of the seed record, to verifydetails, and/or to collect additional information. The notification mayprovide the user with instructions to verify/add details, such as a URLthe user needs to visit, a phone number to call, or the like.

Processing continues at 210 where additional data and/or verificationdetails are received from the user, and the seed record is converted toan active record in the wallet enrollment system 114. In someembodiments, the additional data obtained at 210 may include informationidentifying a mobile wallet payment application. For example, in someembodiments, an application may be downloaded onto a user's mobiledevice which allows the user to conduct transactions using the digitalwallet. Processing at 210 may include associating information with thespecific application (including information identifying the mobiledevice on which the application has been installed) with the paymentinformation from the seed record.

Pursuant to some embodiments, wallet enrollment may be performed using aseparate hardware device configured to allow wallet enrollments to beperformed at merchant or other transaction locations that have legacypayment terminals (e.g., such as point of sale devices which have notbeen adapted to perform wallet enrollment as described herein).Referring now to FIG. 3 , such a wallet enrollment system 300 is shown.

The wallet enrollment system 300 may include one or more components thatare deployed at a merchant location or at other locations whereconsumers are located and wish to enroll to participate in a digitalwallet program. For example, a wallet enrollment system 300 may includean enrollment device 304 which is located at customer service countersat merchant locations, at bank branches, at events, or the like.Pursuant to some embodiments, a wallet enrollment system 300 may includea legacy payment terminal 302 (such as a electronic cash register, apoint of sale terminal or the like). Pursuant to some embodiments, thewallet enrollment system 300 leverages the processor and communicationsof the legacy payment terminal 302. An enrollment device 304 is incommunication with the legacy payment terminal 302. The enrollmentdevice 304 may be, for example, a computing device with a touch screendisplay interface, such as a tablet computing device (e.g., such as anApple® iPad, or a device using the Android® or Microsoft® Windowsoperating systems). In some embodiments, the enrollment device 304 mayhave a keypad or other data entry device (in addition to or instead of atouch screen).

In some embodiments, the enrollment device 304 (and/or the paymentterminal 302) is in communication with a card reader 306. The cardreader 306 may be, for example, a magnetic stripe reader. The cardreader 306 may be built into a housing of the enrollment device 304 orbe a separate component in communication with the enrollment device 304.For example, the card reader 306 may be coupled to a universal serialbus (“USB”) port of the enrollment device 304 and may be configured toread up to 3 tracks of data from magnetic stripe payment devicespursuant to ANSI/ISO Standards 7810,7811-1/6 and 7813.

The card reader 306 may also be or include a radio frequency identifier(“RFID”) reader, such as one configured to interrogate and read datafrom a contactless mobile device such as one configured to operatepursuant to the PayPass® standard or the like. In some embodiments, thecard reader 306 is shared by the payment terminal 302 and the enrollmentdevice 304. In some embodiments, a separate card reader 306 may beprovided for use with the enrollment device 304.

The enrollment device 304, may be operated in conjunction with thepayment terminal 302 and the reader 306 to perform wallet enrollmentprocessing (e.g., as described above in conjunction with FIG. 1 ). Forexample, the enrollment device 304 may be used to secure consumerconsent to allow payment card data to be transmitted to a walletenrollment system 314 for use in creation or updating of a digitalwallet. In some embodiments, the enrollment device 304 may be operatedseparately from the payment terminal 302 to allow a user to registerpayment account information for use in creating or updating a digitalwallet separate from a payment transaction. For example, a user mayinteract with the enrollment device 304 to swipe or present a paymentcard solely for the purpose of creating or updating a digital walletwith information from that payment card (in which case the enrollmentdevice 304 may communicate the wallet enrollment request messagedirectly to a wallet enrollment system 314 or have the wallet enrollmentrequest message forwarded or routed to the wallet enrollment system 314through the payment terminal 302).

Not all of the components shown in FIG. 3 need be involved in a walletenrollment system 300 of the present invention. For example, in someembodiments, an enrollment device 304 may be in communication with areader 306 to allow a user to create or update digital wallets pursuantto the present invention. For example, in some embodiments, enrollmentdevice 304 may be a standalone device in communication with a reader 306and wallet enrollment system 314 to allow users to swipe or otherwiseread their card(s) and cause the information read from the card(s) to betransmitted (along with customer contact information and opt in data) towallet enrollment system 314. As an illustrative example, an enrollmentdevice 304 may be a tablet computer, a mobile device, a kiosk, adedicated terminal, or the like located at a customer service desk orother convenient location for customers to interact with the enrollmentdevice 304 to present their payment cards for reading to create orupdate digital wallets pursuant to the present invention.

As a further illustrated example, in some embodiments, the walletenrollment device 304 may be a mobile device (including a mobile deviceoperated by the user wishing to create or update a digital wallet). Insuch an embodiment, a mobile wallet registration application may be madeavailable and downloaded and installed onto a mobile device. The mobiledevice, operating the mobile wallet registration application, mayfunction as an enrollment device 304. In some embodiments, the reader306 may be a mobile magnetic stripe reader that attaches to a mobiledevice via a Micro-USB port or an audio jack of the mobile device. Forexample, one suitable reader is an iMag Pro Mobile MagStripe Readeravailable from ID TECH® (or similar devices). In such an embodiment, auser of a mobile device that is configured with a mobile walletregistration application, and which is in communication with a paymentcard reader (including magnetic stripe or other reader technologies),may read payment card information from one or more payment cards andcause the information read from the cards to be transmitted to a walletenrollment system 314 to update or create a digital wallet pursuant tothe present invention. As another illustrative example, in someembodiments, no reader 306 is required. Instead, imaging and capturetechnology available on a mobile device may be used to capture an imageof the face of a payment card. The captured image may then be processedusing image processing software and tools (such as those provided byCard.Io®) to Generate Payment Card Data (Including, for example, thecardholder's name, the PAN, the expiration date, and card image). Thiscaptured data may be transmitted (along with cardholder contactinformation) from the mobile device (acting as an enrollment device 304)to wallet enrollment system 314 to cause the updating or creation of adigital wallet pursuant to the present invention.

The wallet enrollment system 300 may be configured with software toallow consumers to perform wallet enrollment processing. For example,the system 300 may be configured to perform a wallet enrollment processas described in FIG. 4 , in which a process 400 for wallet enrollment isshown.

Process 400 begins at 402 when a consumer interacts with an enrollmentdevice 304 to request a mobile wallet. For example, a consumer may visita location having an enrollment device 304 and interact with a displaymenu on the device. For example, a display screen of the enrollmentdevice 304 may prompt the consumer to “click here to get your mobilewallet” or a similar call to action. An illustrative user interface 500is shown in FIG. 5 , where a user interface 500 that may be displayed ona display screen 502 of an enrollment device 304 is shown. As depictedin FIG. 5 , the user interface 500 prompts the user “To create a mobilewallet or add this payment card to your existing wallet, simply enteryour mobile phone number and press ‘Accept’”. Those skilled in the artwill appreciate that this prompt is illustrative, and that other userinterfaces may be utilized. Further, while a mobile phone number may beused as a customer contact method, other contact methods may also beused.

Processing continues at 404 where the wallet enrollment system 300receives consumer contact information. More particularly, in someembodiments, the consumer is prompted (e.g., by interacting with thedisplay device associated with the enrollment device 304) to enter thephone number of their mobile device on which they wish to install anduse the mobile wallet application. Once the phone number is received,processing continues at 406 where the consumer is prompted to present afirst payment card to be read by the card reader 306. The consumer thenswipes or taps (depending on whether the card is a magnetic stripe cardor an RFID card) a first payment card on reader 306. The card data istransmitted from the enrollment device 304 to a remote wallet enrollmentplatform for processing. The card data (such as, for example, Track 1and Track 2 data from a magnetic stripe payment card) are read by thereader 306, passed to the enrollment device 304 for association with theinformation entered by the consumer (e.g., the mobile phone numberentered by the consumer), and transmitted to the remote walletenrollment platform so that the data may be used to store the card datain the consumer's mobile wallet.

If the card is read properly and the card data is successfully captured,processing continues at 408 where the consumer is prompted to answerwhether they wish to add another payment card to their wallet. If “yes”,processing reverts to 406 and the consumer is prompted to presentanother card to the reader 306. If no further cards are to be added tothe consumer's wallet, processing continues at 410 where a mobile walletinstallation message is transmitted to the consumer.

For example, the mobile wallet installation message may be transmittedto the consumer as an email message (if the consumer provided theiremail address), as an SMS message, or the like. The mobile walletinstallation message may provide a link directing the consumer todownload and install the mobile wallet application of the presentinvention on their mobile device. In some embodiments, the mobile walletis pre-loaded with information about the consumer's enrolled paymentcards.

In some embodiments, the mobile wallet installation message may bepresented to the consumer on the display device of the enrollment device304. For example, a QR code may be generated which encodes a URL to adownload location for the mobile wallet application (which may bepersonalized for the consumer). The consumer may be prompted to operatetheir mobile device and scan the QR code to initiate download andinstallation of the mobile wallet application.

When the mobile wallet application is downloaded onto the consumer'smobile device, an installer may launch the application and prompt theconsumer for information to complete the enrollment process. Forexample, the consumer may be prompted to validate themselves. As onespecific validation example, a consumer may be presented with severaladdresses that may be associated with their payment card(s) (several ofwhich are invalid) and prompted to select their correct address. If theconsumer properly identifies their correct address, the consumer isvalidated and the mobile wallet application installation process maycomplete and the mobile wallet may be used for use in paymenttransactions.

Embodiments of the present invention as shown and described inconjunction with FIGS. 3-5 provide an upgrade path for merchants that donot have point of sale terminals that are capable of being updated withwallet enrollment software or applications.

The above descriptions of processes herein should not be considered toimply a fixed order for performing the process steps. Rather, theprocess steps may be performed in any order that is practicable,including simultaneous performance of at least some steps.

Although the present invention has been described in connection withspecific exemplary embodiments, it should be understood that variouschanges, substitutions, and alterations apparent to those skilled in theart can be made to the disclosed embodiments without departing from thespirit and scope of the invention as set forth in the appended claims.

The invention claimed is:
 1. A system, comprising: a processor; and anon-transitory computer-readable medium having instructions storedthereon that are executable by the processor to cause the system toperform operations comprising: collecting, from a merchant point-of-sale(POS) device through a secure application programming interface (API) ofthe system, one or more digital wallet messages comprising electroniccontact information and digital payment information in association witha transaction conducted by a person at the merchant POS device, whereinthe digital payment information identifies a first funding instrumentused to pay for the transaction, and wherein the first fundinginstrument has a primary account number; formatting the digital paymentinformation in a digital format where the primary account number is notrecorded with a seed record; creating the seed record for the digitalpayment information from the one or more digital wallet messages,wherein the seed record comprises the electronic contact information andthe formatted digital payment information in the digital format, andwherein the seed record comprises a partial record requiring additionalinformation to be an active record for use by the system; storing theseed record; identifying a mobile device number or an email address fromthe electronic contact information; generating a link configured todirect the person to a user interface to create the digital wallet usingthe seed record; transmitting, to the mobile device number or the emailaddress of the electronic contact information, a digital wallet creationrequest containing the link; detecting, from a mobile devicecorresponding to the electronic contact information of the person, aselection of the link configured to direct the person to the userinterface; converting, based on the additional information, the seedrecord to the active record with the system, wherein the active recordincludes the additional information from the person; creating, based onthe converting, the digital wallet for the person from the active recordwithout requiring user input in the mobile application for the firstfunding instrument for use with the digital wallet; and adding, from theformatted digital payment information, the first funding instrument tothe digital wallet, wherein the digital wallet is configured to allowthe addition of a plurality of different funding instruments usable toconduct transactions, and wherein primary account numbers of thedifferent funding instruments are not stored within the digital wallet.2. The system of claim 1, wherein the operations further comprise:transmitting an indication to the person that the digital wallet hasbeen created and is ready for use.
 3. The system of claim 1, wherein theoperations further comprise: receiving a request for an electronicpayment transaction to be made using the digital wallet; accessing thedigital payment information for the first funding instrument; andcompleting the electronic payment transaction using the first fundinginstrument.
 4. The system of claim 1, wherein the operations furthercomprise: receiving second digital payment information collected via adifferent merchant POS device in association with a second transactionconducted by the person at the different merchant POS device, the seconddigital payment information identifying a second funding instrumentdifferent from the first funding instrument and that was used to pay forthe second transaction, wherein the second funding instrument has asecond primary account number; and adding the second funding instrumentto the digital wallet, wherein the second primary account number is notstored within the digital wallet.
 5. The system of claim 1, wherein theformatted digital payment information utilizes at least a proxyidentifier instead of the primary account number.
 6. The system of claim1, wherein the electronic contact information comprises the mobiledevice number entered to the merchant POS device during the transaction.7. The system of claim 1, wherein the email address is identified fromthe electronic contact information.
 8. A method, comprising: collecting,from a merchant point-of-sale (POS) device through a secure applicationprogramming interface (API) of the system, one or more digital messagescomprising electronic contact information and digital paymentinformation in association with a transaction conducted by a person atthe merchant POS device, wherein the digital payment informationidentifies a first funding instrument used to pay for the transaction,and wherein the first funding instrument is associated with an accountnumber; formatting the digital payment information in a digital formatwhere the account number is not recorded with a seed record; generating,by a computer system, the seed record for the digital paymentinformation from the one or more digital messages, wherein the seedrecord comprises the electronic contact information and the formatteddigital payment information in the digital format, and wherein the seedrecord comprises a partial record requiring additional information to bean active record for use by the computer system; identifying, by thecomputer system, a mobile device number or an email address from theelectronic contact information; generating a link configured to directthe person to a user interface to convert the seed record to the activerecord; transmitting, by the computer system to the mobile device numberor the email address, a digital wallet request containing the link;detecting, by the computer system from a mobile device corresponding tothe electronic contact information of the person, a selection of thelink configured to direct the person to the user interface; generating,by the computer system and based on the additional information, theactive record from the seed record, wherein the active record includesthe additional information from the person; and adding, by the computersystem based on the formatted digital payment information, the firstfunding instrument to the digital wallet or the person from the activerecord without requiring user input in the mobile application for thefirst funding instrument, wherein the digital wallet is configured toallow the addition of a plurality of different funding instrumentsusable to conduct transactions, and wherein account numbers of thedifferent funding instruments are not stored within the digital wallet.9. The method of claim 8, wherein the digital payment informationincludes an expiration date for the first funding instrument.
 10. Themethod of claim 8, further comprising: creating, by the computer system,the digital wallet responsive to the digital wallet request and based onthe additional information.
 11. The method of claim 8, wherein theadditional information includes a user consent to create the digitalwallet.
 12. The method of claim 8, further comprising: sending, by thecomputer system, a text message to the mobile device number, wherein thelink in the text message includes a network address accessible by amobile phone device to download and install a phone applicationconfigured to allow access to the user interface and the digital wallet.13. The method of claim 12, further comprising: transmitting, by thecomputer system, an indication to the person, via the phone applicationinstalled on the mobile phone device, that the first funding instrumenthas been added to the digital wallet.
 14. The method of claim 8, whereinthe digital payment information is collected from a payment card viamagnetic swipe.
 15. The method of claim 8, wherein the digital paymentinformation is collected from a payment device via a wireless protocol.16. The method of claim 15, wherein the wireless protocol comprises aradio frequency identification (RFID) protocol.
 17. The method of claim8, wherein the digital payment information is collected from a captureof an image of a payment card.
 18. A non-transitory computer-readablemedium having instructions stored thereon that are executable to cause acomputer system to perform operations comprising: collecting, from amerchant point-of-sale (POS) device through a secure applicationprogramming interface (API) of the system, one or more messagescomprising electronic contact information and digital paymentinformation in association with a transaction conducted by a person atthe merchant POS device, wherein the digital payment informationidentifies a first funding instrument used to pay for the transaction,and wherein the first funding instrument is associated with an accountnumber; formatting the digital payment information in a digital formatwhere the account number is not recorded with a seed record; generating,from the one or more messages, the seed record comprising a partialrecord requiring additional information to be an active record for useby the computer system, wherein the partial record comprises theelectronic contact information and the formatted digital paymentinformation; identifying a mobile device number or an email address fromthe electronic contact information; generating a link configured todirect the person to a user interface to create a digital wallet usingthe seed record; transmitting, to the mobile device number or the emailaddress, a digital wallet creation request containing the link;detecting, from a mobile device corresponding to the electronic contactinformation of the person, a selection of the link configured to directthe person to the user interface; generating the active record from theseed record with the computer system, wherein the active record includesthe additional information from the person; creating, based on theactive record, the digital wallet for the person from the active recordwithout requiring user input in the mobile application for the firstfunding instrument for use with the digital wallet; and adding, from theformatted digital payment information, the first funding instrument tothe digital wallet, wherein the digital wallet and is configured toallow the addition of a plurality of different funding instrumentsusable to conduct transactions, and wherein account numbers of thedifferent funding instruments are not stored within the digital wallet.19. The non-transitory computer-readable medium of claim 18, wherein theoperations further comprise: transmitting an indication, to the mobiledevice number or the email address, that the digital wallet has beencreated and is ready for use.
 20. The non-transitory computer-readablemedium of claim 18, wherein the operations further comprise: receiving arequest for an electronic payment transaction to be made using thedigital wallet; accessing the digital payment information for the firstfunding instrument; and completing the electronic payment transactionusing the first funding instrument.